Selective compression of data for uplink to a telecommunication network

ABSTRACT

A computer-implemented method for selectively excluding data from compression prior to uplink to a telecommunication system. In an embodiment, the method analyzing a request by an application, executing within a device, to wirelessly uplink data to a telecommunication node. The method further includes establishing a set of logical channels assigned to the application. The method further includes transferring the data among one or more logical channels, of the set of logical channels, based on a status flag related to data compression corresponding to the data. The method further includes determining that the data is transferred via a compression-disabled logical channel, of the set of logical channels. The method further includes responding to determining that the data is transferred via the compression-disabled logical channel by bypassing a data compression function prior to preparing the data for uplink. The method further includes uplinking the data to the telecommunication node.

BACKGROUND OF THE INVENTION

The present invention relates generally to the field of transmittingdata to a telecommunication system, and in particular to managingcompression of data to uplink to a next generation telecommunicationnode.

Mobile telecommunication systems were initially developed to provide avoice service while guaranteeing activity of a user. Mobiletelecommunication systems have evolved to provide text and data servicesin addition to voice services. Increases in the number and demands ofusers of advanced mobile devices has generated a dramatic increase oftraffic and higher-speed/bandwidth service requirements. For example,telecommunication advances have been key enablers for many technologiesincluding video streaming and artificial intelligence (AI) to succeed byreducing or eliminating various limiting factors, such as sedentaryoperations, lower bandwidth communications, etc. Advances associatedwith fifth generation (5G) telecommunication technologies are expectedto serve as enablers to push dependent technologies to higher levelperformance and capabilities through mobile bandwidths of 1 GBPS(gigabits/second) or greater, convergence of Internet-of-things (IoT)device access, etc.

5G new radio (NR) is a radio access technology designed as the wirelessair interface of 5G networks. In 5G NR the medium access control (MAC)layer provides services to the radio link control (RLC) layer. Oneservice of the MAC layer service provides logical channels to the RLClayer, which further enables the creation of multiple logical channelsover a single radio bearer network using 5G network slicing models. Somelogical channels carry control information and other logical channelconvey data traffic from the 5G-enabled user equipment (UE) to a 5Gnetwork node (i.e., a base station). In addition, the 5G-enabled networknode can utilize logical channels linked to the UE to process packetscorresponding to different data at differing “quality of service” (QoS)among designated logical channels.

SUMMARY

According to an aspect of the present invention, there is acomputer-implemented method, computer program product, and/or system forselectively compressing data to uplink to a telecommunication system. Inan embodiment the method includes at least one computer processoranalyzing a request by an application, executing within a device, towirelessly uplink data to a telecommunication node. The method furtherincludes at least one computer processor establishing a set of logicalchannels assigned to the application. The method further includes atleast one computer processor transferring the data among one or morelogical channels, of the set of logical channels, based on a status flagrelated to data compression corresponding to the data. The methodfurther includes at least one computer processor set of logicalchannels. The method further includes at least one computer processorresponding to determining that the data is transferred via thecompression-disabled logical channel by bypassing a data compressionfunction prior to preparing the data for uplink. The method furtherincludes at least one computer processor uplinking the data to thetelecommunication node.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a wireless telecommunication communicationenvironment, in accordance with an embodiment of the present invention.

FIG. 2 a flowchart of steps of a dedicated traffic channel managementprogram, in accordance with an embodiment of the present invention.

FIG. 3 depicts a flowchart of steps of a packet data convergenceprotocol management program, in accordance with an embodiment of thepresent invention.

FIG. 4 is a block diagram of components of a computer, in accordancewith an embodiment of the present invention.

DETAILED DESCRIPTION

Embodiments of the present invention recognize that one feature offifth-generation new radio telecommunication technology (5G NR) is theautomatic compression of data within 5G-enabled user equipment (UE),such as smartphone, tablet computers, and other wireless devices priorto transmission. Embodiments of the present invention recognize that 5GNR technology enables the packet data convergence protocol (PDCP) within5G NR-enabled UEs to capture and compress data (i.e., payload) packetsfrom upper layer protocols in the UE stack and also compress the uplinkpackets prior to transmission over the radio (e.g., wireless) interface.However, embodiments of the present invention recognize that the payloadcompression mechanism included within the PDCP sub-layer of a 5G-enabledUE collects the upcoming packets for transmission and performs data(payload) compression on each data packet coming from upper layer of the5G system stack without considering the effects to both the UE and theuser utilizing the UE, such as increased power consumption and slowerresponse time.

Embodiments of the present invention also recognize that within 5Gtelecom network, the medium access control (MAC) sub-layer of 5G NRprovides services to the Radio Link Control (RLC) sub-layer controls areprovided in the form of logical channels. Embodiments of the presentinvention recognize that the logical channels are virtualizedcommunication network interfaces that are used to transfer I0 commands(e.g., network data packets) and control instructions over radiointerface of a 5G fixed access network. A logical channel is defined bythe type of information it carries and is generally differentiated as acontrol channel, used for transmission of control and configurationinformation; or a traffic channel used to communicate data. Embodimentsof the present invention also recognize that 5G NR technology allows forthe creation of multiple logical channels over a single radio bearernetwork using the 5G network slicing models. The multiple logicalchannels are used to carry a specialized traffic from 5G NR-enable UEdevice to an evolved node B (eNodeB) of the 5G network. As multiplelogical channels are created from a single device to the 5G eNodeB, themultiple logical channels deliver parallelism in the packet transmissionas well as reducing the exclusive locking of the 5G network resourcesthat gives performance benefits.

In addition, embodiments of the present invention recognize that anotherfeature of 5G NR technology enables individual software applications tocreate dedicated logical channels to transmit data over NR interfacefrom the application layer to a 5G eNodeB. In such an implementation,the dedicated traffic channels of an application transmit packets toPDCP sub-layer and subsequent lower protocols transfer the data to adestination (e.g., UEs or an eNodeB) over Radio. Once the data issubmitted to PDCP sub-layer, the PDCP sub-layer performs data alignmentand convergence of data packets prior to forwarding the prepared datapackets to RLC controls.

However, embodiments of the present invention further recognize that the5G NR stack dictates that all the data packets are compressed beforedata convergence at PDCP, which is a highly CPU intensive activity andconsumes a lot of processor power. Further, the dictated compression ofdata adds additional latency to the packet data transmission over RadioBearer until reaching the serving gateway (SGW). Further, today 5G NRtechnology does not include a mechanism for selective data payloadcompression at PDCP that saves the computing resources and reduces thepower consumption of the UE. There is no communication between anapplication, service data adaptation protocol (SDAP) sub-layer, and PDCPsub-layer regarding compressibility information related to upcoming datafor uplink traffic, which lead to further inefficiency in the 5G RAN.

Embodiments of the present invention utilize the 5G UE User Plane (UP)stack, the SDAP sub-layer, DTCH controller, and the PDCP sub-layer ofthe 5G UP protocol to enable selective compression of uplinked packetpayloads while still executing instances of robust header compression(RoHC) protocol for header information, and PDCP ciphering for data fromdesignated applications. Some embodiment of the present invention canexclude (i.e., bypass) low compression ratio data packets from the PDCPpayload compression function by DTCH identification and selectivelycompressing the data payload from certain DTCH logical channels thatsends compression efficient packets to a lower layer. Thus, embodimentsof the present invention save the computation bandwidth at a UE,improves CPU and memory resource utilization, and reduces the overallpower consumption of the UE as PDCP child instances are instructed forselective compression.

The descriptions of the various scenarios, instances, and examplesrelated to the present invention have been presented for purposes ofillustration but are not intended to be exhaustive or limited to theembodiments disclosed.

The present invention will now be described in detail with reference tothe Figures. FIG. 1 is a functional block diagram illustrating wirelesstelecommunication communication environment 100, in accordance withembodiments of the present invention. In an embodiment, wirelesstelecommunication communication environment 100 includes, user equipment(UE) 110 and telecommunication node 130 interconnected via wirelesscommunications 120. In addition, wireless telecommunicationcommunication environment 100 includes network 140 interconnect totelecommunication node via network link 135.

User equipment (UE) 110 may be a laptop computer, a tablet computer, anetbook computer, a personal computer, a desktop computer, a personaldigital assistants (PDA), a smart phone, a wearable device (e.g., smartglasses, a smart watch, an e-textile, an AR headsets), a wirelessrouter, a medical device, a fitness device, an entertainment console orany programmable computer system known in the art. In certainembodiments, UE 110 represents a computer system utilizing clusteredcomputers and components (e.g., database server computers, applicationserver computers, storage area networks) that act as a single pool ofseamless resources, as is common in data centers and withcloud-computing applications.

In general, UE 110 is representative of any programmable electronicdevice or combination of programmable electronic devices capable ofexecuting machine readable program instructions and wirelesslycommunicating with telecommunication node 130. System 110 may includecomponents, as depicted and described in further detail with respect toFIG. 4, in accordance with embodiments of the present invention.

UE 110 includes telecommunication support 112, applications (apps) 113,data 114, mapped tables 116, dedicated traffic channel (DTCH) managementprogram 200, packet data convergence protocol (PDCP), management program300, and other programs and data (not shown). In addition, UE 110 canestablish wireless communications 120 with telecommunication node 130.Examples of other programs and data include an operating system (OS), acamera program, a media player, a contact list, communication programs,etc. In some embodiments, UE 110 includes additional hardware andfeatures (not shown), such as one or more cameras, a speaker, amicrophone, a compass, an inertial monitoring system, a globalpositioning system (GPS), and/or other features associated with a mobiledevice.

Telecommunication support 112 includes hardware, software, and firmwarefeatures (not shown) that can generate wireless signal 121 to establishwireless communications 120 with telecommunications node 130 utilizing5G NR technology. In addition, telecommunication support 112 alsoincludes hardware, software, and firmware features (not shown) thatprovide support for 5G NR technology, such as a DTCH controller, aciphering module, various sub-layers and services (discussed above), andother features and services known in the art. In some embodiments,telecommunications support 112 also includes one or more peripherals oradapters that support 5G NR wireless technology operatively coupled toan instance of UE 110 that originally lacked wireless communicationcapabilities or lacked support for 5G NR technology.

Applications (Apps) 113 represent a plurality of apps (e.g., mobiledevice applications) installed within UE 110. For example, apps 113 mayinclude an e-mail app, a productivity suite (e.g., a word processor, aspreadsheet, a presentation program, etc.), one or more social mediaapps, a camera app, a dictation app, etc. In some embodiments, an app ofapps 113 can output data in more than one format, resolution, and/ordegree of compression. In a further embodiment, an app of apps 113represents an application program interface (API) or other programexecuting external to UE 110, such as a web app that request to uplinkdata from data 114.

In an embodiment, one or more apps of apps 113 generate and/or outputdata that is uplinked (i.e., transmitted) to a 5G network viatelecommunication node 130. In one scenario, a first app of apps 113generates data in-situ, such as a text message, or a live stream videoand creates a request to uplink the data to a 5G network. In anotherscenario, second app of apps 113 generates data, such as picture takenby a camera app and stored within a photo gallery, audio recoded via adictation app, a document generated by a word processing app that isstored within data 114. Subsequently, a user or another app utilizes athird app creates a request to uplink the data to a 5G network. In oneexample, a user creates a social media post the includes a photo storedwithin data 114. In another example, a calendar app can initiate ane-mail to a group of users that includes a document, such as a renewalnotice stored within data 114.

Data 114 is representative of a plurality of data that a user orapplication can be uplinked to telecommunication node 130. Data 114 mayinclude a gallery of pictures, documents, screen captures, a contactlist, previously downloaded information, web links, media files, etc. Insome embodiments, data 114 also includes metadata related to one or moreitems stored within data 114, such as an app that generated the data;information indicating whether a potentially compressible data formatwas pre-compressed by the app that generated the data; informationrelated to the content included within an item of data, such as onepresentation including a high percentage of text as opposed to a secondpresentation including a high percentage multi-media content andanimated elements.

Mapped tables 116 includes a set tables, lists, and/or associativearrays utilized to interrelate various source of information associatedwith 5G NR uplinks of data. In an embodiment, one or more tables ofmapped tables 116 interrelate an application (app) ID, a data type, acompression status flag (e.g., apply the PDCP payload data compressionfunction, excluded data compression by the PDCP payload data compressionfunction), logical channel IDs and DTCH IDs. In one embodiment, DTCHprogram 200 creates or updates one or more tables or a group of fieldswithin mapped tables 116. For example, each DTCH_CREATE, DTCH_MODIFY,and DTCH_DISCONNECT operation triggers an update to mapped tables 116 tomaintain consistency among functions and services. Subsequently, PDCPprogram 300 utilize mapped tables 116 to selectively control whethercompression is applied to data or data packets prior to uplink totelecommunication node 130.

In some embodiments, mapped tables 116 also includes a table or a listof data types and/or file formats that further includes indications orflags that signify that a data type/file format is uncompressed (e.g.,is compressible), is compressed (e.g., is not compressible), or ispotentially compressible. For example, with respect to image files, bmpformat is uncompressed, tiff format is compressed, and jpeg format maybebe compressible. In addition, some file formats that are highlycompressible and other formats can be compressed to a limited degree.For example, encryption makes a file appear more random, so compressionis less effective/efficient. In another embodiment, mapped tables 116further includes another table or another list that associates acompression ratio value or other metric associated with a data type/fileformat and/or app as determined during prior executions of PDCPmanagement program 300. In a further embodiment, mapped tables 116includes another flag associated with data compression that indicatesthat the data (e.g., a plurality of data packets) for uplink includesboth data packets that are compressible and data packets excluded fromcompression.

DTCH management program 200 that analyzes a request to uplink data by anapp to determine whether the data is processed by one or more logicalchannels designate to transfer data subject to data compression (i.e.,compression-enabled channels) or one or more logical channels designatedto transfer data excluded from compression (i.e., compression-disabledchannels) prior to uplink the data to a 5G NR telecommunication node,such as telecommunication node 130. In an embodiment, DTCH managementprogram 200 is associated with the SDAP sub-layer and/or the PDCPsub-layer and interfaces telecommunication support 112 to establishescontact between UE 110 and telecommunication node 130. In addition, DTCHprogram 200 transmits information relate to data to uplink, such aswhether a logical channel transfers compressed data or data that wasexcluded from compression, a quantity of data to uplink (affectsquantity DTCHs created), etc., to telecommunication node 130.

Responsive to DTCH program 200 establishing wireless communications 120between UE 110 and telecommunication node 130, DTCH program 200 receivesan ID corresponding to each DTCH created by telecommunication node 130for UE 110. DTCH management program 200 also maintains one or moretables within mapped tables 116 that interrelate app IDs, DTCH IDs, andrespective status flags related to data compression.

In various embodiments, DTCH program 200 interfaces with PDCP managementprogram 300 to prepare and uplink data based on a compression statusflag respectively associated with the app, data, and/or datatype/fileformat included within mapped tables 116. In a further embodiment, DTCHprogram 200 can request that telecommunication node 130 create aplurality of DTCHs (i.e., logical channels) links between UE 110 andtelecommunication node 130 to process packets of corresponding todifferent data and/or requesting apps at differing “quality of service”(QoS).

PDCP management program 300 selectively excludes data (i.e., datapackets) within the PDCP sub-layer from the PDCP payload compressionfunction prior to uplink to a 5G telecommunication system based oninformation included within mapped tables 116, such as compressionstatus flags respectively associated with an app of apps 113, datagenerated by an app, and/or data utilized by an app. PDCP managementprogram 300 can also utilize and/or execute functions and servicesincluded within the PDCP sub-layer, such as transfers of data (userplane or control plane), maintenance of PDCP instance PIDs, headercompression and decompression using the ROHC protocol, ciphering anddeciphering, integrity protection, integrity verification, etc.

In an embodiment, PDCP management program 300 can also monitor thecompression ratio of data packets by of the compression mechanism nativeto the PDCP sub-layer and update a table or list within mapped tables116 for a given data type/file format or an app that generated data. Insome embodiments, PDCP management program 300 can reroute the databetween logical channels assigned to an app based on previouslydetermined compression ratio values included within another table orlist within mapped tables 116 and other factors, such as the batterylife remaining within UE 110 and/or a latency dictate. In a furtherembodiment, PDCP management program 300 can independently process datapackets of the plurality of data packets that comprise the data touplink based on the compression status flag assigned to each logicalchannels and a segmentation analysis of the data to uplink.

In an embodiment, wireless communications 120 includes wireless signals121 produced by UE 110, element 122 representing control channelsbetween UE 110 and telecommunication node 130, and element 123representing dedicated traffic channels the uplink data from UE 110 totelecommunication node 130. In various embodiments, wirelesscommunications 120 are based on a 5G NR technology architecture.

Wireless signals 121 represents a plurality of communicationstransmitted from UE 110 to telecommunication node 130, such as requeststo establish a wireless link between UE 110 and telecommunication node130, requests to establish control and dedicated traffic channels forutilized to uplink data (i.e., element 123), etc. In addition, wirelesssigns also represent the receipt of wireless communications fromtelecommunication node 130, such as element 122.

In and embodiment, element 122 (double headed arrow) represents a set ofone or more control channels associated with establishing communicationsand conveying messages between UE 110 and telecommunication node 130,such as handshakes, a DTCH_CONNECT request, control instructions relatedto compression status flags, DTCH_CREATE requests, DTCH_ID informationgenerated within telecommunication node 130, payload receipt acknowledgemessages, transfers messages, etc.

Examples of control channels within element 122 include a broadcastcontrol channel (BCCH), a downlink channel for broadcasting systemcontrol information; a paging control channel (PCCH), a downlink channelthat carries paging messages; a common control channel (CCCH), channelfor transmitting control information between UE 100 andtelecommunication node 130; a dedicated control channel (DCCH), apoint-to-point bi-directional channel that transmits dedicated controlinformation between UE 110 and telecommunication node 130.

In an embodiment, element 123 (group of four dashed lines) represents aset of created dedicated traffic channels (DTCHs) utilized to uplinkdata packets from UE 110 to telecommunication node 130. In variousembodiments, the DTCHs represented by element 123 are identified with acorresponding DTCH ID assigned by telecommunication node 130, andfurther associated with a status flag corresponding to each DTCH ID thatindicates whether a DTCH uplinks compressed data to telecommunicationnode 130 or a DTCH that uplinks data to telecommunication node 130excluded from compression.

In an embodiment, telecommunication node 130 is eNodeB transceiverstation (e.g., base station) of a 5G telecommunication networkassociated with network link 135 and network 140. In an embodiment,telecommunication node 130 includes other hardware, computing equipment,and software (not shown) that enables 5G NR wireless communications witha plurality of instances of UE 110, and provide various functions andservices. Instances of telecommunication node 130 may includecomponents, as depicted and described in further detail with respect toFIG. 4, in accordance with embodiments of the present invention.

Examples of functions and services provided by telecommunication node130 include but are not limited to as radio bearer control, radioadmission control, connection mobility control, dynamic allocation ofresources to UEs for both uplink and downlink (e.g., scheduling), IPheader compression/decompression, packet and/or dataencryption/decryption, integrity protection of data, connection setupand release (e.g., quantity of DTCHs to create, DTCH ID assignments,etc.), scheduling and transmission of paging messages and/or systembroadcast information, metadata class/function table maintenance,support of network slicing, QoS flow management and mapping to dataradio bearers, radio access network sharing, etc. For example,telecommunication node 130 includes a metadata table that identifies theDTCH IDs that correspond to traffic channels that received compresseddata payloads and traffic channels that include data payloads that wereexcluded from data compression.

Network link 135 is representative of one or more communicationsinterconnections between telecommunication node 130 and network 140.Network link 135 may operate via wired, wireless, or optical connectionsand can be any combination of connections and protocols (described infurther detail with respect to network 140).

Network 140 can be, for example, a local area network (LAN), atelecommunications network (e.g., a portion of a cellular network), awireless local area network (WLAN), such as an intranet, a wide areanetwork (WAN), such as the Internet, or any combination of the previousand can include wired, wireless, or fiber optic connections. In general,network 140 can be any combination of connections and protocols thatwill support communications between telecommunication node 130 and othernetworks and endpoints (not shown), in accordance with embodiments ofthe present invention. In various embodiments, at least a portion ofnetwork 140 operates locally via wired, wireless, or optical connectionsand can be any combination of connections and protocols (e.g., personalarea network (PAN), Bluetooth®, near field communication (NFC), laser,infrared, ultrasonic, etc.).

In various embodiments, telecommunication node 130, network link 135,and network 140 represent a portion of a 5G telecommunication networkthat receives, and forwards data uplinked from UE 110 to another networkand/or one or more endpoints (not shown). Examples of other networks andendpoints that include but are not limited to the Internet; an intranetof an enterprise; a wirelessly accessible device of another user; suchas a smart phone, a tablet computer, a wearable device (e.g., smartglasses, a wireless headset, etc.), a smart TV, etc.

FIG. 2 is a flowchart depicting operational steps for dedicated trafficchannel (DTCH) management program 200, a program that establishes a setof wireless communication channels to uplink data from a mobile deviceof a user to a 5G telecommunication node, in accordance with embodimentsof the present invention. In various embodiments, DTCH managementprogram 200 calls (i.e., executes) an instance of packet dataconvergence protocol (PDCP) management program 300 to selectivelycompress and uplink data to the 5G telecommunication node for each appthat request to uplink data. In some embodiments, DTCH managementprogram 200 is included as a new function or service within the SDAPsub-layer or is associated with telecommunication support 112, such asvia a firmware update to the DTCH controller (not shown) of UE 110.

In step 202, DTCH management program 200 receives a request to uplinkdata. In one embodiment, DTCH management program 200 receives a requestto uplink data to a 5G telecommunication network from a user of UE 110via an app of apps 113. In another embodiment, DTCH management program200 receives an automated request to uplink data to a 5Gtelecommunication network from another app of apps 113, such as acalendar app. For example, DTCH program 200 may detect that aDTCH_CONNECT request arrives at the DTCH controller (not shown) of UE110. In some embodiments, DTCH management program 200 processes aplurality of requests to uplink data from two or more apps of apps 113.DTCH management program 200 may process data uplink requests fromconcurrently executing app and/or apps that execute during the samesession (i.e., link) between UE 110 and telecommunication node 130.

In step 204, DTCH management program 200 analyzes the request to uplinkdata. In addition, DTCH management program 200 analyzes the request touplink data to determine other information related to the request touplink data, such as a PID corresponding to an app or app instance,quantity of data to upload, a QoS dictated associated with the request,a quantity of logical channels assigned to process the data to uplink,etc. In one embodiment, DTCH management program 200 analyzes the requestto uplink data by enquiring the app that created the request todetermine whether the data associated with the uplink request isexcluded from compression. In another embodiment, DTCH managementprogram 200 analyzes the request to uplink data by an app based oninformation included among mapped tables 116, such as identifying acompression status flag associated with an app and/or a give datatype/file format.

In a further embodiment, DTCH management program 200 analyzes therequest to uplink data and determines that the data generated by an appor selected from among the plurality of data within data 114 includes acombination of data or a plurality of data packets that includes a firstgroup of data or data packets that are compressible and a second groupof data or data packets excluded from data compression prior to uplink.DTCH management program 200 may also determine that some data related tothe request is flagged as potentially compressible or of a reducedcompression ratio.

In step 206, DTCH management program 200 establishes a set of logicalchannels. In an embodiment, DTCH management program 200 establishes aset of logical channels internal to UE 110, based on the request touplink data, such as a quantity of dedicated traffic channels utilizedto transfer (e.g., handle or process) the data associated with therequest. DTCH management program 200 assigns (e.g., allocates) differentsets of logical channels to each app of apps 113 that requests to uplinkdata to a 5G telecommunication network via telecommunication node 130.In some embodiments, DTCH management program 200 also associates a QoSto a set of logical channels.

In step 208, DTCH management program 200 assigns a flag to a channel.DTCH management program 200 assigns a compression status flag to eachchannel of the set of logical channels designating whether a logicalchannel processes (e.g., handles) data to compress prior to uplink orthat the logical channel processes data excluded from compression priorto uplink. In one embodiment, DTCH management program 200 assign thesame compression status flag to each logical channel of set of logicalchannels assigned to an app. In another embodiment, DTCH managementprogram 200 assigns differing compression status flags among the set oflogical channels assigned to an app based on the quantity of data tocompress prior to uplink and the quantity of data excluded fromcompression prior to uplink.

In step 210, DTCH management program 200 interfaces with atelecommunication node. In an embodiment, DTCH management program 200interfaces (e.g., establishes wireless communications 120) withtelecommunication node 130 via wireless signals 121. For example, DTCHmanagement program 200 utilizes an aspect of telecommunications support112, such as a channel manager (not shown) that performs a radioresource allocation and messaging telecommunications node 130 bysignaling DTCH_CONNECT followed by a DTCH creation tasks (i.e.,DTCH_CREATE). DTCH management program 200 exchanges parameters and otherinformation respectively associated with a set logical channels withtelecommunication node 130. In response, DTCH management program 200receives a set of DTCH IDs corresponding to the logical channelsassigned to each app uplinking data to telecommunication node 130.

In step 212, DTCH management program 200 updates a table. In anembodiment, DTCH management program 200 updates one or more tables andlists based on information related to a request to uplink data andinformation received from telecommunication node 130, such as a PIDcorresponding to an app or an app instance, a compression statusassigned to a DTCH ID, one or more data compression status flagsassociated with data generated by an app for uplink and/or selected byan app for uplink to a 5G telecommunication network; and/or informationassociated with the plurality of data within data 114.

In step 214, DTCH management program 200 executes PDCP managementprogram 300. In addition, DTCH management program 200 pushes one or moreupdated tables of mapped tables 116 to a PDCP instance manager (notshown) that assigns a process ID (PID) to a corresponding PDCP instanceand a logical channel or a set of logical channels. In an embodiment,DTCH management program 200 executes PDCP management program 300 toselectively compress and uplink data to telecommunication node 130. Insome embodiments, DTCH management program 200 executes an instance ofPDCP management program 300 for each app that requests to upload dataduring a given period of time or link between UE 110 andtelecommunication node 130.

FIG. 3 is a flowchart depicting operational steps for PDCP managementprogram 300, a program that selectively excludes data and/or datapackets from the PDCP payload compression function prior to uplink to a5G telecommunication node, in accordance with embodiments of the presentinvention. In various embodiments, multiple instances of PDCP managementprogram 300 can execute concurrently to process data for uplink fromdifferent apps or instances of one or more apps. In some embodiments,PDCP management program 300 is included as a new function or servicewithin the PDCP sub-layer or is added to UE 110 via a firmware or OSupdate that can disable the PDCP payload compression function for one ormore child instances of PDCP.

In step 302, PDCP management program 300 receives application data touplink. In an embodiment, PDCP management program 300 receives data touplink (i.e., transmission) to a 5G telecommunication system, such asnode 130 and network 140 to forward another network and/or one or moreendpoints based on information related to a request to uplink dataprocessed by DTCH management program 200. In one scenario, PDCPmanagement program 300 receives data generated by an app of apps 113 touplink. In another scenario, PDCP management program 300 receives dataselected by an app of apps 113 to uplink from among the plurality ofdata within data 114.

In step 304, PDCP management program 300 identifies an application IDcorresponding to data to data to uplink. In an embodiment, PDCPmanagement program 300 identifies an application (app) ID correspondingto data to uplink based on information included within one or moreupdated mapped tables pushed to PDCP management program 300 by DTCHmanagement program 200. In various embodiments, PDCP management program300 also determines the one or more DTCH IDs that are assigned to theapp requesting to uplink data to a 5G telecommunication system.

In step 306, PDCP management program 300 determines compressibilityinformation related to received data. PDCP management program 300 maysegment the data for analysis and/or transfer among logical channels. Inone embodiment, PDCP management program 300 determines compressibilityinformation related to the data received from an app for uplink based oninformation corresponding to one or more logical channels that areassign to the app, such a compression status flag respectivelyassociated with a set of logical channels. In another embodiment, PDCPmanagement program 300 determines compressibility information related toreceived data, such as an PID correspond to the app associated with arequest to uplink data to a 5G telecommunication system and/or metadatainformation included within data 114 associate with the data receivedfrom an app to uplink to the 5G telecommunications system.

In some embodiments, PDCP management program 300 determinescompressibility information related to data received from an app touplink based on other information within included within data 114 and/ormapped tables 116. In one scenario, PDCP management program 300identifies a non-binary compression status flag (e.g., data ispotentially compressible) based on information and/or metadata includedwithin data 114. In another scenario, PDCP management program 300determines that the data received from an app is excluded from the PDCPpayload compression function based on a data type/file formatcorresponding to the received data. In some scenarios, PDCP managementprogram 300 determines that the data received from an app includes somedata packets that are excluded from payload compression and other datapackets that can be compressed. In a further embodiment, PDCP managementprogram 300 determines whether the data receive from an app is or is notsubject to PDCP payload compression based on other factors, such aspreviously determined compression ratio values associated with a givendata type/file format and/or an app.

In decision step 307, PDCP management program 300 determines whetherdata is compressible. In one embodiment, PDCP management program 300determines that the data (e.g., data packet payload) received from anapp to uplink is compressible based on a corresponding compressionstatus flag or the data is assigned to a logical channel designated forprocessing compressible data. In another embodiment, PDCP managementprogram 300 determines that the received data associated with an appuplink request is not compressible (i.e., excluded from datacompression) based on a corresponding compression status flag or thedata is assigned to a logical channel designated for processing dataexcluded from compression. (e.g., based on the data format and/or theapplication that generated the data).

In a further embodiment, PDCP management program 300 determines that astream of data to uplink from an application includes of plurality(e.g., combinations) of data packets of differing characteristics, suchimage data, document/content data, voice data, etc. In response, PDCPmanagement program 300 can dynamically (i.e., on-the-fly) route thepackets of the stream of data among compression-enabled logical channelsand logical channels excluded from compression based on the flagassigned to one or more packets of data. PDCP management program 300 canalso adjust the routing of data packets or data segments among logicalchannels based on other factors, such as reducing overall latency andpower consumption by excluding all packets of the received data fromdata compression or compressing data to reduce the cost to the user ofUE 110 associated with transmitting the data via a 5G telecommunicationsystem.

Responsive to determining that data is compressible (Yes branch,decision step 307), PDCP management program 300 forwards the data to acompression-enabled channel (step 308).

In step 308, PDCP management program 300 forwards the data to acompression-enabled channel. In one embodiment, PDCP management program300 forwards (i.e., transfers) the data to the compression-enabledlogical channel assigned to the app that requests to uplink the data toa 5G telecommunication system. In another embodiment, PDCP managementprogram 300 distributes the data among one or more compression-enabledlogical channels assigned to the app that requests to uplink the data toa 5G telecommunication system. In some embodiments, PDCP managementprogram 300 forwards the dynamically routed data packets of the data touplink among the one or more compression-enabled logical channelsassigned to the app based on compressibility a compression status flagassigned to a data packet.

In step 310, PDCP management program 300 compresses an uplink payloaddata packet. In an embodiment, PDCP management program 300 permits thePDCP payload compression function to compress an uplink payload datapacket received via a compression-enabled logical channel. In a furtherembodiment, PDCP management program 300 also monitors the effect of thePDCP payload compression function on the data and determines acompression ratio value. Subsequently, PDCP management program 300updates mapped tables with the determined compression ratio valuerespectively associated with an app and/or a data type/file format.

Referring to decision step 307, responsive to determining that data isnot compressible (No branch, decision step 307), PDCP management program300 forwards the data to a compression-disenabled channel (step 311). Inanother embodiment, responsive to determining that some data packets ofthe data for uplink are not compressible, PDCP management program 300forwards the data packets that are not compressible or excluded fromcompression to one or more compression-disenabled logical channels (step311).

In step 311, PDCP management program 300 forwards the data to acompression-disenabled channel. In one embodiment, PDCP managementprogram 300 forwards (i.e., transfers) the data, flagged to exclude fromdata compression, to a compression-disenabled logical channel assignedto the app requesting to uplink the data to a 5G telecommunicationnetwork. In another embodiments, PDCP management program 300 distributesthe data, flagged to exclude from data compression, among one or morecompression-disenabled logical channels assigned to the app thatrequests to uplink the data to a 5G telecommunication system. In someembodiments, PDCP management program 300 forwards the dynamically routeddata packets of the data, flagged to exclude from data compression,among the one or more compression-disabled logical channels assigned tothe app based on compressibility a compression status flag assigned to adata packet.

In various embodiments, responsive to forwarding (i.e., transferring)data to one or more compression-disabled logical channels, PDCPmanagement program 300 also bypasses or disables the PDCP payloadcompression function of a child instance of PDCP from affecting the datatransferred via the one or more compression-disabled logical channelsassigned to the app.

In step 312, PDCP management program 300 prepares uplink packets fortransmission. In an embodiment, PDCP management program 300 preparesdata packets for uplink by adding compression status flag to the headerand executing one or more services and/or functions of the PDCPsub-layer, such as packet alignment, applying uplink packed headerinformation, header compression (e.g., utilizing the RoHC protocol),ciphering and other data convergence activities. In addition, PDCPmanagement program 300 further associated the uplink data packets withthe one or more DTCH IDs assigned to the app associated with the data.

In step 314, PDCP management program 300 transmits a packet of data to atelecommunication node. In an embodiment, PDCP management program 300utilizes one or more functions and/or services of the RLC sub-layer tointerface with telecommunication support 112 to uplink data packets totelecommunication node 130 via the set of DTCH IDs respectivelyassociated with an app ID (represented by element 123) and further basedon respectively data compression status flags associated with the DTCHIDs within mapped tables 116. In addition, PDCP management program 300indicates to telecommunication node 130 that data uplink is complete byexecuting a DTCH_DISCONNECT operation via a control channel representedby element 122 and updates mapped tables 116 with the logical channelresource release. In response, telecommunication node 130 performsvarious resource management tasks based on the information associatedwith the DTCH_DISCONNECT operation executed by UE 110.

FIG. 4 depicts computer system 400, which is representative of UE 110and a portion (not shown) of telecommunication node 130. Computer system400 is an example of a system that includes software and data 412.Computer system 400 includes processor(s) 401, cache 403, memory 402,persistent storage 405, communications unit 407, input/output (I/O)interface(s) 406, and communications fabric 404. Communications fabric404 provides communications between cache 403, memory 402, persistentstorage 405, communications unit 407, and input/output (I/O)interface(s) 406.

Communications fabric 404 can be implemented with any architecturedesigned for passing data and/or control information between processors(such as microprocessors, communications and network processors, etc.),system memory, peripheral devices, and any other hardware componentswithin a system. For example, communications fabric 404 can beimplemented with one or more buses, such as a peripheral componentinterconnects (PCI) bus, or a crossbar switch.

Memory 402 and persistent storage 405 are computer readable storagemedia. In this embodiment, memory 402 includes random-access memory(RAM). In general, memory 402 can include any suitable volatile ornon-volatile computer readable storage media. Cache 403 is a fast memorythat enhances the performance of processor(s) 401 by holding recentlyaccessed data, and data near recently accessed data, from memory 402.

Program instructions and data used to practice embodiments of thepresent invention may be stored in persistent storage 405 and in memory402 for execution by one or more of the respective processor(s) 401 viacache 403. In an embodiment, persistent storage 405 includes a magnetichard disk drive. Alternatively, or in addition to a magnetic hard diskdrive, persistent storage 405 can include a solid-state hard drive, asemiconductor storage device, a read-only memory (ROM), an erasableprogrammable read-only memory (EPROM), a flash memory, or any othercomputer readable storage media that is capable of storing programinstructions or digital information.

The media used by persistent storage 405 may also be removable. Forexample, a removable hard drive may be used for persistent storage 405.Other examples include optical and magnetic disks, thumb drives, andsmart cards that are inserted into a drive for transfer onto anothercomputer readable storage medium that is also part of persistent storage405. Software and data 412 are stored in persistent storage 405 foraccess and/or execution by one or more of the respective processor(s)401 via cache 403 and one or more memories of memory 402. With respectto UE 110, software and data 412 includes telecommunication support 112,apps 113, data 114, mapped tables 116, DTCH management program 200, PDCPmanagement program 300, and other programs and data (not shown). Withrespect to telecommunications node 130, software and data 412 includes5G NR software, firmware, metadata tables, and other programs and data(not shown).

Communications unit 407, in these examples, provides for communicationswith other data processing systems or devices, including resources of UE110 and various portions of telecommunication node 130. In theseexamples, communications unit 407 includes one or more network interfacecards. Communications unit 407 may provide communications, through theuse of either or both physical and wireless communications links. In anembodiment, communications unit 407 generates wireless communications120. Program instructions and data used to practice embodiments of thepresent invention may be downloaded to persistent storage 405 throughcommunications unit 407.

I/O interface(s) 406 allows for input and output of data with otherdevices that may be connected to each computer system. For example, I/Ointerface(s) 406 may provide a connection to external device(s) 408,such as a keyboard, a keypad, a touch screen, and/or some other suitableinput device. External device(s) 408 can also include portable computerreadable storage media, such as, for example, thumb drives, portableoptical or magnetic disks, and memory cards. Software and data used topractice embodiments of the present invention can be stored on suchportable computer readable storage media and can be loaded ontopersistent storage 405 via I/O interface(s) 406. I/O interface(s) 406also connect to display 409.

Display 409 provides a mechanism to display data to a user and may be,for example, a computer monitor. Display 409 can also function as atouch screen, such as the display of a tablet computer or a smartphone.Alternatively, display 409 displays information to a user based on aprojection technology, such as virtual retinal display, a virtualdisplay, or image projector.

The programs described herein are identified based upon the applicationfor which they are implemented in a specific embodiment of theinvention. However, it should be appreciated that any particular programnomenclature herein is used merely for convenience, and thus theinvention should not be limited to use solely in any specificapplication identified and/or implied by such nomenclature.

The present invention may be a system, a method, and/or a computerprogram product. The computer program product may include a computerreadable storage medium (or media) having computer readable programinstructions thereon for causing a processor to carry out aspects of thepresent invention.

The computer readable storage medium can be a tangible device that canretain and store instructions for use by an instruction executiondevice. The computer readable storage medium may be, for example, but isnot limited to, an electronic storage device, a magnetic storage device,an optical storage device, an electromagnetic storage device, asemiconductor storage device, or any suitable combination of theforegoing. A non-exhaustive list of more specific examples of thecomputer readable storage medium includes the following: a portablecomputer diskette, a hard disk, a random-access memory (RAM), aread-only memory (ROM), an erasable programmable read-only memory (EPROMor Flash memory), a static random-access memory (SRAM), a portablecompact disc read-only memory (CD-ROM), a digital versatile disk (DVD),a memory stick, a floppy disk, a mechanically encoded device such aspunch-cards or raised structures in a groove having instructionsrecorded thereon, and any suitable combination of the foregoing. Acomputer readable storage medium, as used herein, is not to be construedas being transitory signals per se, such as radio waves or other freelypropagating electromagnetic waves, electromagnetic waves propagatingthrough a waveguide or other transmission media (e.g., light pulsespassing through a fiber-optic cable), or electrical signals transmittedthrough a wire.

Computer readable program instructions described herein can bedownloaded to respective computing/processing devices from a computerreadable storage medium or to an external computer or external storagedevice via a network, for example, the Internet, a local area network, awide area network and/or a wireless network. The network may comprisecopper transmission cables, optical transmission fibers, wirelesstransmission, routers, firewalls, switches, gateway computers and/oredge servers. A network adapter card or network interface in eachcomputing/processing device receives computer readable programinstructions from the network and forwards the computer readable programinstructions for storage in a computer readable storage medium withinthe respective computing/processing device.

Computer readable program instructions for carrying out operations ofthe present invention may be assembler instructions,instruction-set-architecture (ISA) instructions, machine instructions,machine dependent instructions, microcode, firmware instructions,state-setting data, or either source code or object code written in anycombination of one or more programming languages, including an objectoriented programming language such as Smalltalk, C++ or the like, andconventional procedural programming languages, such as the “C”programming language or similar programming languages. The computerreadable program instructions may execute entirely on the user'scomputer, partly on the user's computer, as a stand-alone softwarepackage, partly on the user's computer and partly on a remote computeror entirely on the remote computer or server. In the latter scenario,the remote computer may be connected to the user's computer through anytype of network, including a local area network (LAN) or a wide areanetwork (WAN), or the connection may be made to an external computer(for example, through the Internet using an Internet Service Provider).In some embodiments, electronic circuitry including, for example,programmable logic circuitry, field-programmable gate arrays (FPGA), orprogrammable logic arrays (PLA) may execute the computer readableprogram instructions by utilizing information of the computer readableprogram instructions to personalize the electronic circuitry, in orderto perform aspects of the present invention.

Aspects of the present invention are described herein with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems), and computer program products according to embodiments of theinvention. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer readable program instructions.

These computer readable program instructions may be provided to aprocessor of a general-purpose computer, special purpose computer, orother programmable data processing apparatus to produce a machine, suchthat the instructions, which execute via the processor of the computeror other programmable data processing apparatus, create means forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks. These computer readable program instructionsmay also be stored in a computer readable storage medium that can directa computer, a programmable data processing apparatus, and/or otherdevices to function in a particular manner, such that the computerreadable storage medium having instructions stored therein comprises anarticle of manufacture including instructions which implement aspects ofthe function/act specified in the flowchart and/or block diagram blockor blocks.

The computer readable program instructions may also be loaded onto acomputer, other programmable data processing apparatus, or other deviceto cause a series of operational steps to be performed on the computer,other programmable apparatus or other device to produce a computerimplemented process, such that the instructions which execute on thecomputer, other programmable apparatus, or other device implement thefunctions/acts specified in the flowchart and/or block diagram block orblocks.

The flowchart and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods, and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof instructions, which comprises one or more executable instructions forimplementing the specified logical function(s). In some alternativeimplementations, the functions noted in the blocks may occur out of theorder noted in the Figures. For example, two blocks shown in successionmay, in fact, be accomplished as one step, executed concurrently,substantially concurrently, in a partially or wholly temporallyoverlapping manner, or the blocks may sometimes be executed in thereverse order, depending upon the functionality involved. It will alsobe noted that each block of the block diagrams and/or flowchartillustration, and combinations of blocks in the block diagrams and/orflowchart illustration, can be implemented by special purposehardware-based systems that perform the specified functions or acts orcarry out combinations of special purpose hardware and computerinstructions.

The descriptions of the various embodiments of the present inventionhave been presented for purposes of illustration, but are not intendedto be exhaustive or limited to the embodiments disclosed. Manymodifications and variations will be apparent to those of ordinary skillin the art without departing from the scope and spirit of the invention.The terminology used herein was chosen to best explain the principles ofthe embodiment, the practical application or technical improvement overtechnologies found in the marketplace, or to enable others of ordinaryskill in the art to understand the embodiments disclosed herein.

What is claimed is:
 1. A computer-implemented method comprising:analyzing, by one or more computer processors, a request by anapplication, executing within a device, to wirelessly uplink data to atelecommunication node; establishing, by one or more computerprocessors, a set of logical channels assigned to the application;transferring, by one or more computer processors, the data among one ormore logical channels, of the set of logical channels, based on a statusflag related to data compression corresponding to the data; determining,by one or more computer processors, that the data is transferred via acompression-disabled logical channel, of the set of logical channels;responsive to determining that the data is transferred via thecompression-disabled logical channel, bypassing, by one or more computerprocessors, a data compression function prior to preparing the data foruplink; and uplinking, by one or more computer processors, the data tothe telecommunication node.
 2. The computer-implemented method of claim1, wherein the device and the telecommunication node each supportfifth-generation new radio (5G NR) architecture functions and servicesrelated to preparing data for transmission and establishing wirelesscommunications.
 3. The computer-implemented method of claim 1, whereinanalyzing the request to wirelessly uplink the data to thetelecommunication node further comprises: identifying, by one or morecomputer processors, a process ID (PID) corresponding to the applicationrequesting to uplink data to the telecommunication node; determining, byone or more computer processors, compressibility information related tothe data associated with the request; and determining, by one or morecomputer processors, a quantity of logical channels utilized to processthe data for uplink.
 4. The computer-implemented method of claim 1,wherein establishing the set of logical channels assigned to theapplication further comprises: transmitting, by one or more computerprocessors, a message to a 5G telecommunication node to create a set ofone or more dedicated traffic channels (DTCHs) based on the request touplink the data to the 5G telecommunication node, wherein the messagefurther includes: a process ID (PID) corresponding to the application; aquantity of DTCHs to assign to the device; and a respective status flagrelated to data compression corresponding to each logical channel thattransfers the data of the application for uplink; and responsive totransmitting the message to the 5G telecommunication node, receiving, byone or more computer processors, from the 5G telecommunication node, aDTCH ID corresponding to each of the one or more DTCHs assigned to thedevice, wherein each DTCH ID is mapped, within a table, to the PIDcorresponding the application and further to the each logical channelthat transfers the data for the application.
 5. The computer-implementedmethod of claim 1, wherein the status flag related to data compressionis selected from the group consisting of: a compression-enabled statusflag and a compression-disabled status flag.
 6. The computer-implementedmethod of claim 2, wherein 5G data compression is performed by a payloadcompression function included within a packet data convergence protocol(PDCP) sub-layer included within the 5G NR architecture included in thedevice.
 7. The computer-implemented method of claim 4, wherein the datais uplinked to the 5G telecommunication node via one or more dedicatedtraffic channels (DTCHs) assigned to the device by the 5Gtelecommunication node.
 8. The computer-implemented method of claim 1,wherein preparing the data for uplink further comprises: segmenting, byone or more computer processors, the data into a plurality of datapackets; and applying, by one or more computer processors, headerinformation to each data packet of the plurality of data packets,wherein the header information further includes the status flag relatedto data compression corresponding to the data.
 9. A computer programproduct comprising: one or more computer readable storage media andprogram instructions stored on the one or more computer readable storagemedia, the program instructions readable/executable by one or morecomputer processors: program instructions to analyze a request by anapplication, executing within a device, to wirelessly uplink data to atelecommunication node; program instructions to establish a set oflogical channels assigned to the application; program instructions totransfer the data among one or more logical channels, of the set oflogical channels, based on a status flag related to data compressioncorresponding to the data; program instructions to determine that thedata is transferred via a compression-disabled logical channel, of theset of logical channels; responsive to determining that the data istransferred via the compression-disabled logical channel, programinstructions to bypass a data compression function prior to preparingthe data for uplink; and program instructions to uplink the data to thetelecommunication node.
 10. The computer program product of claim 9,wherein the device and the telecommunication node each supportfifth-generation new radio (5G NR) architecture functions and servicesrelated to preparing data for transmission and establishing wirelesscommunications.
 11. The computer program product of claim 9, whereinprogram instructions to analyze the request to wirelessly uplink thedata to the telecommunication node further comprises: programinstructions to identify a process ID (PID) corresponding to theapplication requesting to uplink data to the telecommunication node;program instructions to determine compressibility information related tothe data associated with the request; and program instructions todetermine a quantity of logical channels utilized to process the datafor uplink.
 12. The computer program product of claim 9, wherein programinstructions to establish the set of logical channels assigned to theapplication further comprise: program instructions to transmit a messageto a 5G telecommunication node to create a set of one or more dedicatedtraffic channels (DTCHs) based on the request to uplink the data to the5G telecommunication node, wherein the message further includes: aprocess ID (PID) corresponding to the application; a quantity of DTCHsto assign to the device; and a respective status flag related to datacompression corresponding to each logical channel that transfers thedata of the application for uplink; and responsive to transmitting themessage to the 5G telecommunication node, program instructions toreceive, from the 5G telecommunication node, a DTCH ID corresponding toeach of the one or more DTCHs assigned to the device, wherein each DTCHID is mapped, within a table, to the PID corresponding the applicationand further to the each logical channel that transfers the data for theapplication.
 13. The computer program product of claim 9, wherein thestatus flag related to data compression is selected from the groupconsisting of a compression-enabled and compression-disabled.
 14. Thecomputer program product of claim 10, wherein 5G data compression isperformed by a payload compression function included within a packetdata convergence protocol (PDCP) sub-layer included within the 5G NRarchitecture included in the device.
 15. The computer program product ofclaim 12, wherein the data is uplinked to the 5G telecommunication nodevia one or more dedicated traffic channels (DTCHs) assigned to thedevice by the 5G telecommunication node.
 16. A computer systemcomprising: one or more computer processors; one or more computerreadable storage media; and program instructions stored on the computerreadable storage media for execution by at least one of the one or morecomputer processors, the program instructions comprising: programinstructions to analyze a request by an application, executing within adevice, to wirelessly uplink data to a telecommunication node; programinstructions to establish a set of logical channels assigned to theapplication; program instructions to transfer the data among one or morelogical channels, of the set of logical channels, based on a status flagrelated to data compression corresponding to the data; programinstructions to determine that the data is transferred via acompression-disabled logical channel, of the set of logical channels;responsive to determining that the data is transferred via thecompression-disabled logical channel, program instructions to bypass adata compression function prior to preparing the data for uplink; andprogram instructions to uplink the data to the telecommunication node.17. The computer system of claim 16, wherein the device and thetelecommunication node each support fifth-generation new radio (5G NR)architecture functions and services related to preparing data fortransmission and establishing wireless communications.
 18. The computersystem of claim 16, wherein program instruction to analyze the requestto wirelessly uplink data to the 5G telecommunication node furthercomprise: program instructions to identify a PID corresponding to theapplication requesting to uplink data to the 5G telecommunication node;program instructions to determine compressibility information related tothe data associated with the request; and program instructions todetermine a quantity of logical channels utilized to process the datafor uplink.
 19. The computer system of claim 16, wherein programinstructions to establish the set of logical channels assigned to theapplication further comprise: program instructions to transmit a messageto a 5G telecommunication node to create a set of one or more dedicatedtraffic channels (DTCHs) based on the request to uplink the data to the5G telecommunication node, wherein the message further includes: aprocess ID (PID) corresponding to the application; a quantity of DTCHsto assign to the device; and a respective status flag related to datacompression corresponding to each logical channel that transfers thedata of the application for uplink; and responsive to transmitting themessage to the 5G telecommunication node, program instructions toreceive, from the 5G telecommunication node, a DTCH ID corresponding toeach of the one or more DTCHs assigned to the device, wherein each DTCHID is mapped, within a table, to the PID corresponding the applicationand further to the each logical channel that transfers the data for theapplication.
 20. The computer system of claim 17, wherein 5G datacompression is performed by a payload compression function includedwithin a packet data convergence protocol (PDCP) sub-layer includedwithin the 5G NR architecture included in the device.